Printer driver system for remote printing

ABSTRACT

A server for connection to a client via a network, the client being operable to transmit user-input to the server over the network and to receive user-output from the server over the network. The server comprises a network interface for connection to the network; and a processor coupled to the interface. The processor is operable to remotely host execution of an application for the client. The application is for receiving the user-input from the client over the network and for generating the user-output for transmission to the client over the network. The server implements a universal printer driver operable to generate a universal printer file from the application based on a request for a file to be printed that is embedded in the user-input. The server is further operable to transmit the universal printer file over the network. The universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a CONTINUATION of U.S. patent application Ser. No. 11/312,747 to Fu et al., filed on Dec. 21, 2005, now U.S. Pat. No. 7,265,867 which is a CONTINUATION of Ser. No. 09/802,240 to Fu et al., filed on Mar. 8, 2001, now U.S. Pat. No. 7,064,856, hereby incorporated by reference herein.

FIELD OF THE INVENTION

The present invention generally relates to a printer driver system, and more particularly, to a server, method and client-server system for implementing such a system.

BACKGROUND OF THE INVENTION

In the client-server environment, the server operating system is called upon to handle communication interaction with a variety of client-based applications. The client operating system locates a server and requests a connection with the server and the server allocates resources to handle requests from the client. This can include, for example, a print request to a designated printer connected locally or to the client.

Examples of such clients include workstations, desktop computers, laptops, hand held devices and the like. Examples of printer devices include laser printers, bubblejet printers, inkjet printers, multi-purpose machines which combine printing, faxing and/or photocopying capabilities, and the like.

In some client-server systems, however, the client computer is a simple machine that is implemented with less functionality than a general-purpose computer. For instance, the client might be implemented as a terminal, which typically provides just enough functionality to enable access to the server computer over a network. The terminal has no operating system or “intelligence”; rather, the operating system and applications reside at the server, and the processing takes place at the server.

More recently, low cost computers known as “network computers” or “NCs” have been introduced as a means for providing access to a network. Network computers have a display, a keyboard, a network port, and limited processing capabilities. Network computers can provide some limited local processing, but are primarily reliant on the server for most processing. Presently available network computers are primarily configured to run applications written in Java, a language introduced by Sun Microsystems. Closely related to the NCs is another type of low cost computer, known as “Net PCs”, which can run both Windows-based and Java-based applications, but which operate in a similar manner to an NC.

Various technologies, and in particular, a technology marketed under the name “MetaFrame” from Citrix Systems Inc., extend the typical Windows NT server operating system to support multiple client-server windowing sessions for connected clients, where each session provides a windowing environment for the connected client.

With the MetaFrame technology, for example, a client can connect to the Windows NT server and begin a windowing session. To the user, it appears as if the client is a standalone Window-enabled computer that is running its own Windows-brand operating system. However, the session is actually taking place on the server computer, remote from the client, and the client is merely running a local graphical user interface to provide entry to the session. In this regard, the MetaFrame technology is particularly well suited for low intelligent client computers, such as terminals and network-centric computers, because the client need not be capable of running its own operating system. However, the MetaFrame technology is also equally well suited for fully enabled clients.

A server operating system supports multiple client-server sessions and enables each client to work with applications hosted by the server and create and print work to local printers (connected to the server) or remote printers (connected to, for example, the client). It should be noted that an essential component of current client-server printer applications is that the host server must be able to support each of the numerous printers which might be selected. This is usually accomplished by installing the relevant printer driver on the host server.

However, issues evolving from the installation of printer drivers on the host server include the volume of printer devices on the market, the stability of the printer drivers for some devices, the reliability of the server after the installation of numerous printer drivers, and naming conventions of drivers among different operating systems.

A common problem with, for example, the Citrix MetaFrame technology, therefore, is the ability to print to any remote printer device. Another problem with Citrix MetaFrame technology is the bandwidth usage taken by the server when processing a print job to a remote printer since bandwidth and speed are also issues that the host server must deal with when processing remote print jobs.

To exemplify the problem, consider a common scenario. A user logs onto the Windows NT server from a client computer at the user's home. Connected to the user's computer is a multi-purpose printer/fax machine. The user works on a document using word-processing software hosted by the server. The user then wants to print the work to the printer/fax machine connected to the home computer. The print job is processed by the server but it cannot be sent to the user's local printing device because the device is not recognized or supported by the server's operating system or because the printing job requires more bandwidth than is available to send the print job across the connection.

The server must also recognize the type of printer/fax machine and send the print job to it in a recognizable form. The bandwidth available to the server-client must also be sufficient enough to allow for the speedy transfer of the file information.

A similar scenario would be a user that is connected to the host server through a terminal.

It should be noted that printers have their own “language”. When work is sent to a printer, the content of the document is transformed to a format that a printer can recognize, interpret and print out. The most common formats are formats developed by Hewlett Packard, Epson and PostScript. Conversion of the work to a printer format is generally accomplished by the use of a driver which driver is particular to an individual machine and operating system.

This means that for each printing device and operating system, a driver must be installed on the host server in order for it to process print jobs to that printing device. It also means that the file created by the server and sent to the printer can vary in size depending on the type of printer. However, these printer files are typically quite large in nature, and thus generally require significant amounts of bandwidth in order to print at a reasonable speed. Also, due to their large size, the transmission speed of transferring the printer file from the server to the client's printer, can significantly affect the speed at which the print job is completed.

Thus, in summary, a common problem in remote printing is that the printer file is large and, accordingly, requires a large bandwidth to transfer the print job. A second problem is that the server must contain the printer driver files for all printers which may be connected to the computer systems of the remote user. A third problem is that the server must remain stable and reliable when dealing with a wide variety of different printer drivers.

While existing systems have met with some success, there is a desire to improve the printing system to better overcome these problems and to better focus on the needs of the user. In particular, there is a need to overcome these problems in order to reduce the bandwidth load, and to reduce the need for a large number of printer drivers to be stored on the host server.

SUMMARY OF THE INVENTION

A first broad aspect of the invention seeks to provide a server for connection to a client via a network, the client being operable to transmit user-input to the server over the network and to receive user-output from the server over the network. The server comprises a network interface for connection to the network; and a processor coupled to the interface. The processor is operable to remotely host execution of an application for the client. The application is for receiving the user-input from the client over the network and for generating the user-output for transmission to the client over the network. The server implements a universal printer driver operable to generate a universal printer file from the application based on a request for a file to be printed that is embedded in the user-input. The server is further operable to transmit the universal printer file over the network. The universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.

A second broad aspect of the present invention seeks to provide a method, which comprises: receiving a print request at a server from a client remotely connected to the server via a network; processing the print request at the server by corresponding the print request to an application hosted on the server on behalf of the client; using a universal printer driver to create a universal printer file from the application based on the print request; and sending the universal printer file over the network. The universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.

A third broad aspect of the present invention seeks to provide a client-server computer system, comprising: a server comprising a network interface for connection to a network; and a client for connection to the server via the network. The client is operable to transmit user-input to the server over the network and to receive user-output from the server over the network. The server comprises a processor coupled to the interface. The processor is operable to remotely host execution of an application for the client. The application is capable of receiving the user-input from the client over the network and generating the user-output for transmission to the client over the network. The server implements a universal printer driver operable to generate a universal printer file from the application based on a request for a file to be printed that is embedded in the user-input. The server is further operable to transmit the universal printer file over the network. The client implements a universal print file reader capable of interpreting the universal printer file into a printer file suitable for printing by a printing device.

A fourth broad aspect of the invention seeks to provide a server for connection to a client via a network, the client operable to transmit user-input to the server over the network and to receive user-output from the server over the network. The server comprises a network interface for connection to the network; and a processor coupled to the interface. The processor is operable to remotely host execution of an application for the client. The application is for receiving the user-input from the client over the network and for generating the user-output for transmission to the client over the network. The server implements a universal printer driver operable to generate a universal printer file from the application based on a request for a file to be printed that is embedded in the user-input. The server is further operable to transmit the universal printer file to an electronic mail system for delivery of the universal printer file to a destination specified by the client. The universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.

A fifth broad aspect of the invention seeks to provide a method, comprising: receiving a print request at a server from a client remotely connected to the server via a network; processing the print request at the server by corresponding the print request to an application hosted on the server on behalf of the client; using a universal printer driver to create a universal printer file from the application based on the print request; and sending an email message containing the universal printer file to a destination specified by the client. The universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.

A sixth broad aspect of the invention seeks to provide a client-server computer system comprising: a server comprising a network interface for connection to a network; and a client for connection to the server via the network. The client is operable to transmit user-input to the server over the network and to receive user-output from the server over the network. The server comprises a processor coupled to the interface. The processor is operable to remotely host execution of an application for the client. The application is capable of receiving the user-input from the client over the network and generating the user-output for transmission to the client over the network. The server implements a universal printer driver operable to generate a universal printer file from the application based on a request for a file to be printed that is embedded in the user-input. The server is further operable to communicate with an electronic mail system for delivery of the universal printer file to a destination specified by the client. The destination is operable to receive the universal printer file and further operable to implement a universal print file reader capable of interpreting the universal printer file into a printer file suitable for printing by a printing device.

Other features of the present invention, will be apparent from the following description and the accompanying drawings in which like reference numerals depict like elements.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described by reference to the following drawings wherein:

FIG. 1 is an illustration of a client-server computer system showing printing devices connected to the client computer;

FIG. 2 is a flow chart of a print job being processed on a client-server computer system according to the prior art;

FIG. 3 is a flow chart of a print file being processed on a client-server computer system according to an embodiment of the present invention;

FIG. 4 is a alternative arrangement for a client-server computer system according to an embodiment of the present invention; and

FIG. 5 is a further alternative arrangement for a client-server computer system according to an embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS

A printer file is relatively large due to the fact that the content and the page format settings must be transmitted to the printer in a printer language understood by the printer. A function of a universal printer driver is that it is able to compress the printer file into a smaller file which can be transmitted over the network connection (or Internet connections) more rapidly than the original, larger printer file.

Although any level of compression is generally of some assistance in increasing transmission speed and reducing bandwidth, it is preferred that the universal printer driver compress the printer file to a file size which is less than 95%, preferably less than 90%, and more preferably, less than 75% of its original size. Even more preferably, the universal printer driver will compress the printer file to a file size which is less than 50% of its original size.

The universal printer driver is preferably a commonly available program but may also be a proprietary program developed for this application. One commonly available program is available under the trade mark of Adobe Acrobat. Through Adobe Acrobat, a universal printer driver and a universal print file reader are available which can compress a printer file into a “pdf” printer format file for transmission across the network connection, and convert the “pdf” file into a file suitable for printing. The universal print file reader is generally a related product to the universal printer driver.

It should be noted that traditional printer drivers are generally dependent on the operating system under which the computer is operating. Thus, situations can occur wherein, for example, a host server running on Windows NT or Windows 2000 while the local remote client computer is running Windows 95 or 98, and the printer used on the client computer only has printer drivers for Windows 95 or 98. In this situation, even if the printer drivers are installed on the server, the server won't recognize them or support them. In this case, it can be difficult to manage to print to the remote client printer.

In contrast, a universal printer driver is typically one in which the driver is not dependent on the operating system, and can prepare a printer file which can be transmitted to any number of different operating systems.

Further, the universal printer driver can create a file which can be sent to a variety of machines such as computers running Windows operating systems, Apple computers, VAX computers, computers running under a UNIX operating system, thin-client configurations, Network PCs, NCs, PDAs and a variety of other client computer arrangements. Thus, the print driver is universal in that it creates a print file which can be used by almost all commonly available computer makes, models or operating systems.

The present invention is of use in any situation where a remote client is connected to a client-server arrangement. This includes various networked or Internet connections. Of most interest in the present invention however, is an application wherein the universal printer driver is installed on a server running Citrix MetaFrame. Accordingly, the host server may be anyone of a variety of machines capable of acting as a server, but most preferably is a host server capable of running Citrix MetaFrame.

The printer server system generally will comprise a local remote computer which will be directly connected to the printer. However, the printer server system might also comprise a separate computerized system for converting the “pdf” file into a printer file and then sending it directly to the printer without passing through the local, remote computer.

Similarly, the printer file generated by the host server may be converted to the compressed transmittable file in the host server directly. However, the printer file may be sent to a separate computerized system for conversion, before the compressed transmittable file is sent to the remote client computer.

The compressed transmittable file is normally sent directly to the printer server system directly. However, in an alternative embodiment, the compressed transmittable file may be sent to an electronic mail system of the host server, and sent to the client as an e-mail file. The e-mail file can then be printed as normal.

FIG. 1 is an illustration of a client-server computer system, generally depicted as 10, showing printing devices connected to the client computer. In particular, host server 12 is shown having three connection points, namely via a local area network (LAN) 14, via a wide area network (WAN) 15, or via the Internet 16. Connected to LAN network 14 are a plurality of client computers, of which two are shown, namely a desktop PC 20, a laptop PC 30. Each client computer has an attached printer designated as 21 and 31.

Two “thin client” access terminals, generally designated as 42, and a print server 40, are shown as being connected to WAN network 15. Connected to print server 40 are two printers generally designated as 41.

Connected to Internet 16 are a plurality of client computers, of which two are shown, namely a handheld PC 50 (such as a PDA (personal digital assistant) including those sold under the trade name PalmPilot, or e-mail tools such as BlackBerry, or other devices running under Windows CE) and a remote client PC 60. Connected to the client computer systems are printers 51 and 61.

Although variations are possible, this represents a standard configuration for a client-server computer arrangement, and in particular, for a client-server computer arrangement wherein the host server is running a program such as Citrix MetaFrame wherein the remote PC, or the like, is used merely as a terminal to access and use various programs on the host server, and where the host server is used for processing various functions in place of the remote PC.

In FIG. 2, a flow chart of a print job being processed on a client-server computer system of FIG. 1, according to the prior art, is shown. In this example, the user of desktop PC 20 wishes to print a document to PC 21, the flow chart of the actions taken would be as shown in FIG. 2. Initially, the user makes a request for a file to be printed and requests that the file be printed to printer 21. The file is a 15 page document with text and graphics with a size of 142 KB. Server 12 receives the print request, identifies printer 21 and locates the correct driver for printer 21. If the server fails to find the correct driver for the printer, then the print job is abandoned. Only if the correct driver is found, is the print job continued. Using the correct driver, host server 12 prepares a printer file which is then sent to PC 20 over the network connection 14. The printer file for the 15 page document is now 6287 KB in size, and thus creates a large file to be transferred to PC 20. The printer file is then forwarded to printer 21 from PC 20 where it is printed.

In this example, a relatively large printer file is prepared assuming that printer 21 is a printer which is supported by host server 12, and assuming that host server 12 has the correct driver for printer 21. If the printer is not supported and/or the host server does not have the correct driver, then the print request will fail.

In FIG. 3 a similar flow chart is shown of a print file being processed on a client-server computer system according to an embodiment of the present invention. Using the same desktop computer 20, the user makes a request for a file to be printed. Host server 12 receives the print request and uses a universal printer driver to prepare a universal print file for transmission to PC 20 over network connection 14. In this case, the universal printer driver creates a compressed, transmittable printer file having a “pdf” format. The universal print file for the same 15 page document is now 68 KB in size, and takes far less time to be transferred to PC 20. Once the universal print file is received, the user at PC 20 can optionally preview the document and can select the desired printer. The universal printer file reader will then interpret the universal print file, and PC 20 will then forward the universal print file to printer 21 where it is printed.

As is seen, using this approach results in a much smaller file being transferred over network 14, so that the time for transfer is reduced. Also, the host server 12 no longer needs to identify or support printer 21, and does not even need to know which type of printer is to be selected. Host server 12 now merely uses the universal printer driver to create a universal print file. Accordingly, the number of printer drivers stored on the host server 12 is greatly reduced. The remote PC 20 is now used to merely forward the universal print file to the printer 21.

Similar flow charts would be used for any of the remote PC systems shown in FIG. 1, namely PCs 30, 40, 50 and 60, whether connected through the LAN 14, the WAN 15 or the Internet 16, when printing on printers 31, 41, 51, and 61 respectively.

In FIG. 4 an alternative arrangement for a client-server computer system according to an embodiment of the present invention is shown. In FIG. 4, a host server 112 is connected via a LAN 114 to a number of thin client terminals, generally designated as 142. Connected to LAN 114 is a printer server 140, to which is connected printer 141. Also connected to LAN 114 is a WAN 118 to which is connected a series of thin client terminals, of which two are shown, and generally designated as 132. Also connected to WAN 118 is a printer server 130 to which is connected printer 131.

In this embodiment, when a user on a thin client terminal (either 132 or 142) makes a print request, the request is sent to host server 112. Host server 112 uses a universal printer driver to prepare a universal print file. Depending on the printer selected, the universal print file is forwarded to either printer server 130 or printer server 140, from which the universal print file is forwarded to printer 131 or 141 where the file is printed.

Again, in this embodiment, a smaller, compressed universal print file is transmitted over the LAN or WAN rather than the larger printer file. Also, the host server does not need to support the remote printers or have the printer drivers for all of the remote printers which might be used.

Also, it should be noted that it is not necessary for the user's computer to be attached to dedicated printer PC 140. This can be of convenience if the user's computer is a laptop or a hand held PDA, for example, and thus might be removed from its normal printer connection. Additionally, this would allow a wireless connection to the Internet to be used from a mobile PC or PDA which would still allow for printing at a remote printer.

In FIG. 5 a further alternative arrangement for a client-server computer system according to an embodiment of the present invention is shown. This arrangement includes an e-mail server 219 connected to host server 212 through a network 214.

In this embodiment, a print request to the host server 212 from a remote user on PC 220 is received through network 214. In this example, however, the “print job” is to be sent as an e-mail attachment. Host server 212 uses a universal printer driver to create a universal print file with a “pdf” format which is sent through network 214 to e-mail server 219. E-mail server 219 creates an e-mail message 217 which is sent via the Internet 216 to PC 220, where it is received and stored. The universal print file can then be printed at any convenient time on printer 221.

In this fashion, a standard e-mail message can be sent to any party selected by the user, and not just by the user of PC 220, for them to print a universally accepted file on their own printers.

Therefore, having described specific embodiments of the present invention, it will be understood that alternatives, modifications and variations thereof may be suggested to those skilled in the art, and that it is intended that the present specification embrace all such alternatives, modifications and variations as fall within the scope of the appended claims.

Additionally, for clarity and unless otherwise stated, the word “comprise” and variations of the word such as “comprising” and “comprises”, when used in the description and claims of the present specification, is not intended to exclude other additives, components, integers or steps. 

1. A server for connection to a client via a network; said client operable to transmit user-input to said server over said network and to receive user-output from said server over said network; said server comprising: a network interface for connection to said network; a processor coupled to said interface; said processor operable to remotely host execution of an application for said client; said application for receiving said user-input from said client over said network and for generating said user-output for transmission to said client over said network; said server implementing a universal printer driver operable to generate a universal printer file from said application based on a request for a file to be printed that is embedded in said user-input; said server further operable to transmit said universal printer file over said network; said universal printer file having a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.
 2. The server defined in claim 1, wherein the size of the universal printer file is less than the size of the printer file suitable for printing by a printing device.
 3. The server defined in claim 1, wherein the size of the universal printer file is less than 95% of the size of the printer file suitable for printing by a printing device.
 4. The server defined in claim 1, wherein the size of the universal printer file is less than 90% of the size of the printer file suitable for printing by a printing device.
 5. The server defined in claim 1, wherein the size of the universal printer file is less than 75% of the size of the printer file suitable for printing by a printing device.
 6. The server defined in claim l, wherein the size of the universal printer file is less than 50% of the size of the printer file suitable for printing by a printing device.
 7. The server defined in claim 1, wherein said format is in accordance with the Adobe portable document format (“PDF”).
 8. The server defined in claim 1, wherein said universal print file reader is Adobe Acrobat Reader.
 9. The server defined in claim 1, wherein said printing device is locally connected to the client.
 10. The server defined in claim 1, wherein said server and said client run cooperating versions of Citrix MetaFrame; and wherein said user-input, said user-output and said universal printer file are carried over said network via Citrix MetaFrame.
 11. The server defined in claim 1, wherein said application comprises a windowing session for said client.
 12. The server defined in claim 1, wherein said network includes at least one of a local area network; a wide area network and the Internet.
 13. The server defined in claim 1, wherein said universal printer file is carried over said network to said client via email.
 14. A method, comprising: receiving a print request at a server from a client remotely connected to the server via a network; processing the print request at the server by corresponding the print request to an application hosted on the server on behalf of the client; using a universal printer driver to create a universal printer file from the application based on the print request; and, sending the universal printer file over the network; wherein the universal printer file has a format amenable to interpretation by a universal print file reader into a printer file suitable for printing by a printing device.
 15. The method defined in claim 14, wherein the size of the universal printer file is less than the size of the printer file suitable for printing by a printing device.
 16. The method defined in claim 14, wherein the size of the universal printer file is less than 95% of the size of the printer file suitable for printing by a printing device.
 17. The method defined in claim 14, wherein the size of the universal printer file is less than 90% of the size of the printer file suitable for printing by a printing device.
 18. The method defined in claim 14, wherein the size of the universal printer file is less than 75% of the size of the printer file suitable for printing by a printing device.
 19. The method defined in claim 14, wherein the size of the universal printer file is less than 50% of the size of the printer file suitable for printing by a printing device.
 20. The method defined in claim 14, wherein said format is in accordance with the Adobe portable document format (“PDF”).
 21. The server defined in claim 14, wherein said universal print file reader is Adobe Acrobat Reader.
 22. The server defined in claim 14, wherein said printing device is locally connected to the client.
 23. The method defined in claim 14, wherein said server and said client run cooperating versions of Citrix MetaFrame; and wherein said user-input, said user-output and said universal printer file are carried over said network via Citrix MetaFrame.
 24. The method defined in claim 14, wherein said application comprises a windowing session for said client.
 25. The method defined in claim 14, wherein said network includes at least one of a local area network; a wide area network and the Internet.
 26. The method defined in claim 14, wherein said universal printer file is carried over said network to said client via email.
 27. A client-server computer system, comprising: a server comprising a network interface for connection to a network; a client for connection to said server via the network; said client operable to transmit user-input to said server over said network and to receive user-output from said server over said network; said server comprising a processor coupled to said interface; said processor operable to remotely host execution of an application for said client; said application capable of receiving said user-input from said client over said network and generating said user-output for transmission to said client over said network; said server implementing a universal printer driver operable to generate a universal printer file from said application based on a request for a file to be printed that is embedded in said user-input; said server further operable to transmit said universal printer file over said network; said client implementing a universal print file reader capable of interpreting said universal printer file into a printer file suitable for printing by a printing device.
 28. The client-server computer system defined in claim 27, wherein the size of the universal printer file is less than the size of the printer file suitable for printing by a printing device.
 29. The client-server computer system defined in claim 27, wherein the size of the universal printer file is less than 95% of the size of the printer file suitable for printing by a printing device.
 30. The client-server computer system defined in claim 27, wherein the size of the universal printer file is less than 90% of the size of the printer file suitable for printing by a printing device.
 31. The client-server computer system defined in claim 27, wherein the size of the universal printer file is less than 75% of the size of the printer file suitable for printing by a printing device.
 32. The client-server computer system defined in claim 27, wherein the size of the universal printer file is less than 50% of the size of the printer file suitable for printing by a printing device.
 33. The client-server computer system defined in claim 27, wherein said format is in accordance with the Adobe portable document format (“PDF”).
 34. The server defined in claim 27, wherein said universal print file reader is Adobe Acrobat Reader.
 35. The server defined in claim 27, wherein said printing device is locally connected to the client.
 36. The client-server computer system defined in claim 27, wherein said server and said client run cooperating versions of Citrix MetaFrame; and wherein said user-input, said user-output and said universal printer file are carried over said network via Citrix MetaFrame.
 37. The client-server computer system defined in claim 27, wherein said application comprises a windowing session for said client.
 38. The client-server computer system defined in claim 27, wherein said network includes at least one of a local area network; a wide area network and the Internet.
 39. The client-server computer system defined in claim 27, wherein said universal printer file is carried over said network to said client via email. 